Wireless user equipment (UE) capability data transfer between wireless communication networks

ABSTRACT

A wireless communication network serves a User Equipment (UE) and exports UE capability data. A UE Capability Management Function (UCMF) receives the UE capability data and transfers the UE capability data to a Network Exposure Function (NEF). The NEF transfers the UE capability data to another wireless communication network. The UCMF receives additional UE capability data. The NEF receives a UE capability request for the UE from the other wireless communication network. In response, the NEF transfers the UE capability request for the UE to the UCMF. The UCMF transfers additional UE capability data to the NEF. The NEF transfers the additional UE capability data to the other wireless communication network.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless user devicesexecute user applications to support and use the wireless data services.For example, a robot may execute a machine-control application thatcommunicates with a robot controller over a wireless communicationnetwork.

The wireless communication networks have wireless access nodes whichexchange wireless signals with the wireless user devices over radiofrequency bands. The wireless signals use wireless network protocolslike Fifth Generation New Radio (5GNR), Long Term Evolution (LTE),Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WIFI),and Low-Power Wide Area Network (LP-WAN). The wireless access nodesexchange network signaling and user data with network elements that areoften clustered together into wireless network cores. The networkelements comprise Access and Mobility Management Functions (AMFs),Session Management Functions (SMFs), Interworking functions (IWFs), UserPlane Functions (UPFs), Network Exposure Functions (NEFs), ApplicationFunctions (AFs), and the like. The wireless communication networks maycomprise Public Land Mobile Networks (PLMNs) that use different wirelessaccess technologies and different radio frequency bands. The wirelessnetwork elements are grouped into different Dynamic Network Names (DNNs)and wireless network slices.

The wireless user devices come in different types that have differentcapabilities for radio technology, frequency, power, slice, application,and the like. The wireless user devices report their capabilities to thewireless communication networks. The wireless communication networks usethe reported device capabilities to control the radio types,frequencies, power levels, slices, applications, and the like for thewireless user devices. To improve efficiency, the different sets ofdevice capabilities for the different types of wireless user devices aremapped to capability IDs. The wireless communication networks can sharethe specific device capabilities for a specific wireless user device bysharing its capability ID instead of sharing the larger data set thatdescribes all of the device capabilities. The device manufacturers andthe wireless communication networks assign the capability IDs to thewireless user devices.

A User Equipment Capability Management Function (UCMF) stores thecapability IDs for individual wireless user devices and stores the setof device capabilities for the individual capability IDs. Unfortunately,the wireless communication networks do not effectively share capabilityinformation for the wireless user devices. Moreover, home wirelesscommunication networks may be unaware of the capability IDs that areassigned to their wireless user devices by visited wirelesscommunication networks.

TECHNICAL OVERVIEW

A wireless communication network serves a User Equipment (UE) andexports UE capability data. A UE Capability Management Function (UCMF)receives the UE capability data and transfers the UE capability data toa Network Exposure Function (NEF). The NEF transfers the UE capabilitydata to another wireless communication network. The UCMF receivesadditional UE capability data. The NEF receives a UE capability requestfor the UE from the other wireless communication network. In response,the NEF transfers the UE capability request for the UE to the UCMF. TheUCMF transfers additional UE capability data to the NEF. The NEFtransfers the additional UE capability data to the other wirelesscommunication network.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network to transfer UserEquipment (UE) capability data to another wireless communicationnetwork.

FIG. 2 illustrates an exemplary operation of the wireless communicationnetwork to transfer the UE capability data to the other wirelesscommunication network.

FIG. 3 illustrates an exemplary operation of the wireless communicationnetwork to transfer the UE capability data to the other wirelesscommunication network.

FIG. 4 illustrates a visited Fifth Generation (5G) wirelesscommunication network to transfer UE capability data to a home 5Gwireless communication network.

FIG. 5 illustrates the UE in the 5G wireless communication network.

FIG. 6 illustrates the WIFI access node in the 5G wireless communicationnetwork.

FIG. 7 illustrates the LTE access node in the 5G wireless communicationnetwork.

FIG. 8 illustrates a wireless network core in the 5G wirelesscommunication network.

FIG. 9 further illustrates the wireless network core in the 5G wirelesscommunication network.

FIG. 10 illustrates an exemplary operation of the visited 5G wirelesscommunication network to transfer the UE capability data to the homewireless communication network.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 to transfer UserEquipment (UE) capability data to wireless communication network 150.Wireless communication network 100 delivers services to UE 101 likeinternet-access, machine-control, media-streaming, or some other datacommunications product. UE 101 comprises a computer, phone, vehicle,sensor, robot, or some other data appliance with communicationcircuitry. Wireless communication network 100 comprises UE 101, RadioAccess Network (RAN) 121, Access and Mobility Management Function (AMF)122, UE Capability Management Function (UCMF) 123, Network ExposureFunction (NEF) 124, and network functions 125. UE 101 is configured withUE capability data that indicates UE capabilities for Radio AccessTechnology (RAT) types, frequency bands, wireless network slice types,user applications, power ratings, UE class, Session Initiation Protocol(SIP) functionality, user applications, and other UE features. The UEcapability data may comprise a UE Capability ID in Radio CapabilitiesSignaling Optimization (RACS) data.

Various examples of network operation and configuration are describedherein. In some examples, UE 101 wirelessly attaches to RAN 121 andtransfers UE capability data to AMF 122 over RAN 121. The UE capabilitydata describes a set of UE capabilities or indicates a capability IDthat is associated with the set of UE capabilities. UE 101 alsoindicates its UE Identifier (UE ID) and a network ID for network 150 toAMF 122. AMF 122 transfers the UE ID, network ID, and UE capability datato UCMF 123. In some examples, AMF 122 transfers the UE capability datato UCMF 123 in response to detecting that UE 101 is home to wirelesscommunication network 150 and is visiting wireless communication network100. UCMF 123 receives the UE ID, network ID, and UE capability datafrom AMF 122 and responsively transfers the UE ID, network ID, and UEcapability data to NEF 124. In some examples, UCMF 123 transfers the UEcapability data to NEF 124 in response to detecting that UE 101 is hometo wireless communication network 150 and is visiting wirelesscommunication network 100. UCMF 123 may modify the UE capability datalike translating a UE capability set into a UE capability ID ortranslating one UE capability ID into another UE capability ID. NEF 124receives the UE ID, network ID, and UE capability data, and in response,transfers the UE ID and the UE capability data to wireless communicationnetwork 150 based on the network ID. UE 101 transfers the UE ID, networkID, and additional UE capability data to AMF 122 over RAN 121. AMF 122transfers the UE ID, network ID, and additional UE capability data toUCMF 123. In some examples, AMF 122 transfers the additional UEcapability data to UCMF 123 in response to detecting that UE 101 is hometo wireless communication network 150 and is visiting wirelesscommunication network 100. NEF 124 receive a UE capability request forUE 101 from wireless communication network 150 and responsivelytransfers the UE capability request to UCMF 123. In response to the UEcapability request, UCMF 123 responsively transfers the UE ID and theadditional UE capability data to NEF 124. In alternative examples, UCMF123 may transfer the UE ID, network ID, and additional UE capabilitydata to NEF 124 in response to detecting that UE 101 is home to wirelesscommunication network 150 and is visiting wireless communication network100. NEF 124 transfers the UE ID and additional UE capability data tothe wireless communication network 150 in response to the UE capabilityrequest.

Advantageously, wireless communication network 100 effectively shares UEcapability information for UE 101 with wireless communication network150. Moreover, wireless communication network 150 learns the UEcapability IDs that are assigned to UE 101 when UE 101 visits wirelesscommunication network 100.

UE 101 communicates with RAN 121 over technologies like Fifth GenerationNew Radio (5GNR), Long Term Evolution (LTE), Low-Power Wide Area Network(LP-WAN), Institute of Electrical and Electronic Engineers (IEEE) 802.11(WIFI), Bluetooth, Narrowband Internet-of-Things (NB-IoT), and/or someother wireless networking protocol. The wireless communicationtechnologies use electromagnetic frequencies in the low-band, mid-band,high-band, or some other portion of the electromagnetic spectrum. Thecommunication links that interconnect wireless communication network 100use metallic links, glass fibers, radio channels, or some othercommunication media. The communication links use IEEE 802.3 (ENET),Internet Protocol (IP), Time Division Multiplex (TDM), Data Over CableSystem Interface Specification (DOCSIS), General Packet Radio ServiceTransfer Protocol (GTP), 3GPP, 5GNR, LTE, WIFI, virtual switching,inter-processor communication, bus interfaces, and/or some other datacommunication protocols. UE 101 communicates with AMF 122 and networkfunctions 125 over RAN 121. UE 101 may also communicate with AMF 122 andnetwork functions 125 over wireline access networks like InternetService Providers (ISPs).

UE 101 and RAN 121 comprise antennas, amplifiers, filters, modulation,analog/digital interfaces, microprocessors, software, memories,transceivers, bus circuitry, and the like. AMF 122, UCMF 123, NEF 124,and network functions 125 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein.

FIG. 2 illustrates an exemplary operation of wireless communicationnetwork 100 to transfer the UE capability data to the wirelesscommunication network 150. The operation may vary in other examples. AMF122 receives a UE ID, network ID, and UE capability data from UE 101over RAN 121 (201). AMF 122 transfers the UE ID, network ID, and UEcapability data from to UCMF 123 (201). UCMF 123 transfers the UE ID,network ID, and UE capability data to NEF 124 (202). NEF 124 transfersthe UE ID and the UE capability data to wireless communication network150 based on the network ID (203). The process repeats (201).

FIG. 3 illustrates an exemplary operation of wireless communicationnetwork 100 to transfer the UE capability data to other wirelesscommunication network 150. The operation may vary in other examples. Inthis example, UE 101 is home to network 150 and is visiting network 100.UE 101 wirelessly attaches to RAN 121 and registers with AMF 122 using aUE ID, network (NET) ID, and UE capability (CAP) ID. The UE capabilityID is assigned by the UE manufacturer and may be reassigned by wirelesscommunication networks 100 and 150. The UE capability ID is associatedwith a set of RAT types, frequency bands, network slices, userapplications, and the like for UE 101. AMF 122 detects that UE 101 isvisiting wireless communication network 100 from home wirelesscommunication network 150 and attempts to register UE 101 over homenetwork 150. UE 101 and home network 150 may exchange authenticationdata over AMF 122. Home network 150 instructs AMF 122 to serve UE 101.AMF 122 signals RAN 121 and network functions 125 to serve UE 101. RAN121 signals service information to UE 101 like network addresses andquality parameters. UE 101 and RAN 121 exchange user data per thesignaling. RAN 121 and network functions 125 exchange the user data perthe signaling. Network functions 125 and external systems exchange theuser data per the signaling. In response to detecting that UE 101 isvisiting from home network 150, AMF 122 transfers the network ID andRadio Capabilities Signal Optimization (RACS) data to UCMF 123. The RACSdata indicates the UE ID and UE capability ID. UCMF 123 may modify theUE capability ID. UCMF 123 transfers the network ID and the RACS data toNEF 124. The RACs data indicates the UE capability ID reported by UE 101and any UE capability IDs used by network 100 to serve UE 101. NEF 124transfers the RACS data to home wireless communication network 150 basedon the network ID.

In another example, UE 101 wirelessly attaches to RAN 121 and registerswith AMF 122 using the UE ID, network ID, and UE capability ID. AMF 122detects that UE 101 is visiting wireless communication network 100 fromhome wireless communication network 150 and attempts to register UE 101over home network 150. UE 101 and home network 150 may exchangeauthentication data over AMF 122. Home network 150 instructs AMF 122 toserve UE 101. AMF 122 signals RAN 121 and network functions 125 to serveUE 101. RAN 121 signals service information to UE 101 like networkaddresses and quality parameters. UE 101 and RAN 121 exchange user dataper the signaling. RAN 121 and network functions 125 exchange the userdata per the signaling. Network functions 125 and external systemsexchange the user data per the signaling. In response to detecting thatUE 101 is visiting from home network 150, AMF 122 transfers the networkID and RACS data to UCMF 123. The RACS data indicates the UE ID and UEcapability ID. UCMF 123 may modify the UE capability ID. UCMF 123transfers the network ID and the RACS data to NEF 124. NEF 124 receivesa request (RQ) for UE 101 RACS data from home network 150, andresponsively transfers the RACS data for UE 101 to home wirelesscommunication network 150 based on the UE ID and the network ID.

FIG. 4 illustrates visited Fifth Generation (5G) wireless communicationnetwork 400 to transfer UE capability data to home 5G wirelesscommunication network 450. Visited 5G wireless communication network 400comprises an example of wireless communication network 100, althoughnetwork 100 may vary from this example. Visited 5G wirelesscommunication network 400 comprises: visiting UE 401, WIFI AN 420, 5GNRAN 421, Non-Third Generation Partnership Project (N3GPP) IWF 422, Accessand Mobility Management Function (AMF) 423, Session Management Function(SMF) 424, User Plane Function (UPF) 425, UE Capability ManagementFunction (UCMF) 426, Network Exposure Function (NEF) 427, andApplication Function (AF) 428. Home 5G wireless communication network400 comprises AMF 453, UCMF 456, NEF 457, and AF 458.

In a first example, visited 5G network 400 pushes RACS data for visitingUE 401 to home network 450. Visiting UE 401 wirelessly attaches to WIFIAN 420. Visiting UE 401 attaches to N3IWF 422 over WIFI AN 420. VisitingUE 401 registers with AMF 423 over AN 420 and IWF 422. Visiting UE 401transfers its Subscriber Concealed Identifier (SUCI), home Public LandMobile Identifier (PLMN) ID, and UE capability ID to AMF 423. The UEcapability ID is initially assigned by the manufacturer of UE 401 and isassociated with a set of UE features for RAT types, frequency bands,network slices, user applications, and the like. AMF 423 detects thatvisiting UE 401 is from home wireless communication network 450 based onthe PLMN ID and attempts to register UE 401 over home AMF 453. Home AMF453 may authenticate the SUCI for UE 401 and may exchange authenticationdata with visiting UE 401 over visited AMF 423. Home AMF 453 instructsvisited AMF 423 to serve visiting UE 401. Visited AMF 423 signals N3IWF422 and SMF 424 to serve UE 401. SMF 424 signals UPF 425 to serve UE401. AMF 423 signals service information to UE 401 like networkaddresses and quality parameters. Visiting UE 401 and WIFI AN 420exchange user data per the signaling. WIFI AN 420 and N3GPP IWF 422exchange the user data per the signaling. N3GPP IWF 422 and UPF 425exchange the user data per the signaling. UPF 425 and external systemsexchange the user data per the signaling. In response to detecting thatvisiting UE 401 is from home network 450, AMF 423 transfers the PLMN IDfor network 450 and Radio Capabilities Signal Optimization (RACS) datafor visiting UE 401 to UCMF 426. The RACS data indicates the SUCI,International Mobile Equipment Identifier (IMEI), and both the reportedand used UE capability IDs. UCMF 426 may change the UE capability IDwhen serving UE 401. UCMF 426 transfers the PLMN ID and the RACS datafor visiting UE 401 to NEF 427. NEF 427 transfers the PLMN ID and theRACS data for visiting UE 401 to AF 428 over a northbound interface.Based on the PLMN ID, AF 428 transfers the RACS data for visiting UE 401to home AF 458 in home wireless communication network 450. Home AF 458transfers the RACS data for visiting UE 401 to home NEF 457, and NEF 457transfers the RACS data for visiting UE 401 to UCMF 456. UCMF 456 servesthe RACS data to multiple consumers. AFs 428 and 458 could be omittedand NEFs 427 and 457 could communicate directly.

In a second example, home 5G network 450 pulls RACS data for visiting UE401 from visited network 400. Home UCMF 456 subscribes to RACS data forUE 401 from home NEF 457 when UE 401 is visiting other networks. HomeNEF 457 subscribes to RACS data for UE 401 from visited NEF 427 over AFs428 and 458. Visiting UE 401 wirelessly attaches to 5GNR AN 421.Visiting UE 401 registers with AMF 423 over 5GNR AN 421. Visiting UE 401transfers its SUCI, home PLMN ID, and UE capability ID to AMF 423. TheUE capability ID is associated with a set of UE features for RAT types,frequency bands, network slices, user applications, and the like. AMF423 detects that visiting UE 401 is from home wireless communicationnetwork 450 based on the home PLMN ID and attempts to register UE 401over AMF 453. AMF 453 may authenticate the SUCI for UE 401 and mayexchange authentication data with visiting UE 401 over AMF 423. Home AMF453 instructs visited AMF 423 to serve visiting UE 401. AMF 423 signals5GNR AN 421 and SMF 424 to serve visiting UE 401. SMF 424 signals UPF425 to serve UE 401. 5GNR AN 421 and AMF 423 signal service informationto UE 401 like network addresses and quality parameters. Visiting UE 401and 5GNR AN 421 exchange user data per the signaling. 5GNR AN 421 andUPF 425 exchange the user data per the signaling. UPF 425 and externalsystems exchange the user data per the signaling. In response todetecting that visiting UE 401 is from home network 450, AMF 423transfers the PLMN ID for network 450 and RACS data for visiting UE 401to UCMF 426. The RACS data indicates the SUCI, IMEI, and UE capabilityID. In response to the RACS subscription, NEF 427 transfers the RACSdata for visiting UE 401 to NEF 457 over AFs 428 and 458. In response tothe RACS subscription, NEF 457 transfers the RACS data for visiting UE401 to UCMF 456. UCMF 456 serves the RACS data to multiple consumers.AFs 428 and 458 could be omitted and NEFs 427 and 457 could communicatedirectly.

Visited 5G wireless communication network 400 may push RACS data forvisiting UE 401 to home wireless communication network 450 when UE 401attaches to WIFI AN 420 and/or 5GNR AN 421. Likewise, home 5G wirelesscommunication network 450 may pull RACS data for visiting UE 401 fromvisiting wireless communication network 400 when UE 401 attaches to WIFIAN 420 and/or 5GNR AN 421. Using the push and/or pull technique, homeUCMF 456 maintains live RACS data for UE 401 when UE 401 visits accessnodes 420-421 in 5G network 500.

FIG. 5 illustrates UE 401 in 5G wireless communication network 400. UE401 comprises an example of UE 101, although UE 101 may differ. UE 401comprises WIFI radio 501, 5GNR radio 502, processing circuitry 503, anduser components 504. Radios 501-502 comprise antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, memory, andtransceivers that are coupled over bus circuitry. Processing circuitry503 comprises memory, CPU, user interfaces and components, andtransceivers that are coupled over bus circuitry. The memory inprocessing circuitry 503 stores an operating system, user applications(USER), and network applications for IP, 3GPP, WIFI, and 5GNR. Thenetwork applications include physical layer, media access control, linkcontrol, convergence and adaption, radio resource control, and the like.The antennas in WIFI radio 501 are wirelessly coupled to WIFI AN 420over a WIFI link that supports NWu and N1. The antennas in 5GNR radio502 are wirelessly coupled to 5GNR AN 421 over a 5GNR link that supportsRRC and N1. Transceivers (XCVRs) in radios 501-502 are coupled totransceivers in processing circuitry 503. Transceivers in processingcircuitry 503 are coupled to user components 504 like displays,controllers, and memory. The CPU in processing circuitry 503 executesthe operating system, user applications, and network applications toexchange network signaling and user data with respective ANs 420-421over respective radios 501-502.

FIG. 6 illustrates WIFI AN 420 in 5G wireless communication network 400.WIFI AN 420 comprises an example of RAN 121, although RAN 121 maydiffer. WIFI AN 420 comprises WIFI radio 601 and node circuitry 602.WIFI radio 601 comprises antennas, amplifiers, filters, modulation,analog-to-digital interfaces, DSP, memory, and transceivers that arecoupled over bus circuitry. Node circuitry 602 comprises memory, CPU,and transceivers that are coupled over bus circuitry. The memory in nodecircuitry 602 stores operating systems and network applications for IP,WIFI, and 3GPP like physical layer, media access control, link control,and the like. The antennas in WIFI radio 601 are wirelessly coupled toUE 401 over wireless links that support NWu and N1. Transceivers in WIFIradio 601 are coupled to transceivers in node circuitry 602, andtransceivers in node circuitry 602 are coupled to transceivers in IWF422 over links that support NWu and N1. The CPU in node circuitry 602executes the operating system and network applications to exchange dataand signaling with UE 401 and to exchange data and signaling with IWF422.

FIG. 7 illustrates 5GNR AN 421 in 5G wireless communication network 400.5GNR AN 421 comprises an example of RAN 121, although RAN 121 maydiffer. 5GNR AN 421 comprises 5GNR Radio Unit (RU) 701, 3GPP DistributedUnit (DU) 702, and 3GPP Centralized Unit (CU) 703. 5GNR RU 701 comprisesantennas, amplifiers, filters, modulation, analog-to-digital interfaces,DSP, memory, and transceivers that are coupled over bus circuitry. DU702 comprises memory, CPU, and transceivers that are coupled over buscircuitry. The memory in DU 702 stores operating systems and 5GNRnetwork applications that include Physical Layer (PHY), Media AccessControl (MAC), Radio Link Control (RLC), and the like. CU 703 comprisesmemory, CPU, and transceivers that are coupled over bus circuitry. Thememory in CU 703 stores an operating system and network applications forIP and 5GNR that include Packet Data Convergence Protocol (PDCP),Service Data Adaption Protocol (SDAP), Radio Resource Control (RRC), andthe like. The antennas in RU 701 are wirelessly coupled to UE 401 over5GNR links that use various frequency bands and that support RRC and N1.Transceivers in RU 701 are coupled to transceivers in DU 702 overfronthaul links like enhanced Common Public Radio Interface (eCPRI).Transceivers in DU 702 coupled to transceivers in CU 703 over mid-haullinks. Transceivers in CU 703 are coupled to AMF 423 and UPF 427 overbackhaul links. The CPU in DU 703 executes an operating system andnetwork applications to exchange 5GNR data units with RU 701 and toexchange 5GNR data units with CU 703. The CPU in CU 703 executes anoperating system and network applications to exchange the 5GNR dataunits with DU 702, exchange N2/N1 signaling with AMF 423, and exchangeN3 data with UPF 427.

FIG. 8 illustrates wireless network core 800 in 5G wirelesscommunication network 400. Network core 800 comprises an example of AMF122, UCMF 123, NEF 124, and network functions 125, although AMF 122,UCMF 123, NEF 124, and functions 125 may differ. Network core 800comprises Network Function Virtualization Infrastructure (NFVI) hardware801, NFVI hardware drivers 802, NFVI operating systems 803, NFVI virtuallayer 804, and NFVI Virtual Network Functions (VNFs) 805. NFVI hardware801 comprises Network Interface Cards (NICs), CPU, RAM, Flash/DiskDrives (DRIVE), and Data Switches (SW). NFVI hardware drivers 802comprise software that is resident in the NIC, CPU, RAM, DRIVE, and SW.NFVI operating systems 803 comprise kernels, modules, applications,containers, hypervisors, and the like. NFVI virtual layer 804 comprisesvNIC, vCPU, vRAM, vDRIVE, and vSW. NFVI VNFs 805 comprise Non-3GPPInterworking Function (IWF) 822, Access and Mobility Management Function(AMF) 823, Session Management Function (SMF) 824, User Plane Function(UPF) 825, UE Capability Management Function (UCMF) 826, NetworkExposure Function (NEF) 827, and Application Function (AF) 828. OtherVNFs like Authentication Server Function (AUSF) and Network RepositoryFunction (NRF) are typically present but are omitted for clarity.Network core 800 may be located at a single site or be distributedacross multiple geographic locations. The NIC in NFVI hardware 801 arecoupled to ANs 420-421 over data links that support NWu, N3, N2, and N1.The NIC in NFVI hardware 801 are coupled to external data systems overdata links that support N6. NFVI hardware 801 executes NFVI hardwaredrivers 802, NFVI operating systems 803, NFVI virtual layer 804, andNFVI VNFs 805 to form and operate IWF 422, AMF 423, SMF 424, UPF 425,UCMF 426, NEF 427, and AF 428.

FIG. 9 further illustrates wireless network core 800 in 5G wirelesscommunication network 400. IWF 422 performs Y2 termination, N2termination, NWu termination, and N1 transfer. AMF 423 performs N1termination, N2 termination, UE ciphering & integrity protection, UEregistration and connection, LIE mobility and reachability, UEauthentication and authorization, and RACs handling. SMF 424 performs N1termination, session establishment/management, UPF selection, andcontrol, policy and charging control, and traffic steering and routing.UPF 425 performs packet routing & forwarding, packet inspection andpolicy, QoS handling and lawful intercept, PDU interconnection, andmobility anchoring. UCMF 426 manages UE capabilities over AMF APIs andNEF APIs and performs RACS handling. NEF 427 performs capability andevent exposure, data translation/abstraction, control-plane management,AF interaction over the northbound API, and RACs handling. AF 428interact with NEF 424 over the northbound API, communicates with network450 and performs RACs handling.

FIG. 10 illustrates an operation of 5G wireless communication network400 to transfer the UE capability data to wireless communication network450. In the following examples, AFs 428 and 458 are omitted and NEFs 427and 457 directly exchange RACs data. In the first example, visited UCMF426 pushes RACS data for visiting UE 401 to home UCMF 456. In a secondexample, home UCMF 456 pulls RACS data for visiting UE 401 from visitingUCMF 426.

In the first example, visiting UE 401 wirelessly attaches to 5GNR AN421. Visiting UE 401 registers with AMF 423 over 5GNR AN 421. VisitingUE 401 transfers a SUCI, IMEI, PLMN ID, and UE capability ID to AMF 423.In this example, the UE capability ID is assigned by the manufacturer ofUE 401 and is associated with a set of UE features for RAT types,frequency bands, network slices, user applications, and the like thatare supported by UE 401. AMF 423 detects that visiting UE 401 is fromhome wireless communication network 450 based on the PLMN ID andattempts to register UE 401 over home AMF 453. Home AMF 453 mayauthenticate the SUCI for UE 401 and may exchange authentication datawith visiting UE 401 over visited AMF 423. Home AMF 453 instructsvisited AMF 423 to serve visiting UE 401. Visited AMF 423 signals 5GNRAN 421 and SMF 424 to serve UE 101. SMF 424 signals UPF 425 to serve UE401. 5GNR AN 421 and AMF 423 signal service information to UE 401 likenetwork addresses and quality parameters. Visiting UE 401 and 5GNR AN421 exchange user data per the signaling. 5GNR AN 421 and UPF 425exchange the user data per the signaling. UPF 425 and external systemsexchange the user data per the signaling. In response to detecting thatvisiting UE 401 is from home network 450, AMF 423 transfers the PLMN IDfor network 450 and the RACS data for visiting UE 401 to UCMF 426. TheRACS data indicates SUCI, IMEI, and the UE capability ID. UCMF 426 maymodify the UE capability ID for service delivery. UCMF 426 transfers thePLMN ID and the RACS data for visiting UE 401 to NEF 427. NEF 427transfers the PLMN ID and the RACS data for visiting UE 401 to NEF 457based on the PLMN ID. NEF 457 transfers the RACS data for visiting UE401 to UCMF 456. UCMF 456 serves the RACS data for visiting UE 401 tovarious consuming entities.

In the second example, home UCMF 456 subscribes to RACS data for UE 401from home NEF 457 when UE 401 is visiting other networks. Home NEF 457subscribes to RACS data for UE 401 from visited NEF 427. Visiting UE 401wirelessly attaches to 5GNR AN 421. Visiting UE 401 registers with AMF423 over 5GNR AN 421. Visiting UE 401 transfers its UE ID, PLMN ID, andUE capability ID to AMF 423. AMF 423 detects that visiting UE 401 isfrom home wireless communication network 450 based on the home PLMN IDand attempts to register UE 101 over AMF 453. AMF 453 may authenticatethe SUCI for UE 401 and may exchange authentication data with visitingUE 401 over AMF 423. Home AMF 453 instructs visited AMF 423 to servevisiting UE 401. AMF 423 signals 5GNR AN 421 and SMF 424 to servevisiting UE 401. SMF 424 signals UPF 425 to serve UE 401. 5GNR AN 421and AMF 423 signal service information to UE 401 like network addressesand quality parameters. Visiting UE 401 and 5GNR AN 421 exchange userdata per the signaling. 5GNR AN 421 and UPF 425 exchange the user dataper the signaling. UPF 425 and external systems exchange the user dataper the signaling. In response to detecting that visiting UE 401 is fromhome network 450, AMF 423 transfers the PLMN ID for network 450 and RACSdata for visiting UE 401 to UCMF 426. The RACS data indicates the UE IDand UE capability ID(s). In response to the RACS subscription for UE401, NEF 427 transfers the RACS data for visiting UE 401 to NEF 457. Inresponse to the RACS subscription for UE 401, NEF 457 transfers the RACSdata for visiting UE 401 to UCMF 456. UCMF 456 serves the RACS data forvisiting UE 401 to various consuming entities.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose network circuitry toexport UE capability data to other data communication networks like homewireless networks. The computer hardware comprises processing circuitrylike CPUs, DSPs, GPUs, transceivers, bus circuitry, and memory. To formthese computer hardware structures, semiconductors like silicon orgermanium are positively and negatively doped to form transistors. Thedoping comprises ions like boron or phosphorus that are embedded withinthe semiconductor material. The transistors and other electronicstructures like capacitors and resistors are arranged and metallicallyconnected within the semiconductor to form devices like logic circuitryand storage registers. The logic circuitry and storage registers arearranged to form larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose network circuitry toexport UE capability data to other data communication networks like homewireless networks.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communicationnetwork that serves a User Equipment (UE) to export UE capability data,the method comprising: a UE Capability Management Function (UCMF)receiving the UE capability data and a network Identifier (ID) from theAccess AMF and responsively transferring the UE capability data and thenetwork ID to a Network Exposure Function (NEF); the NEF receiving theUE capability data and the network ID, and in response, transferring theUE capability data to another wireless communication network based onthe network ID; the UCMF receiving additional UE capability data; theNEF receiving a UE capability request for the UE from the other wirelesscommunication network and responsively transferring the UE capabilityrequest for the UE to the UCMF; the UCMF receiving the UE capabilityrequest and responsively transferring the additional UE capability datato the NEF; and the NEF receiving the additional UE capability data, andin response to the UE capability request, transferring the additional UEcapability data to the other wireless communication network.
 2. Themethod of claim 1 wherein: the UE comprises a visiting UE; the otherwireless communication network comprises a home wireless communicationnetwork for the visiting UE; and the UE capability data comprises a UEcapability ID that is associated with a set of UE capabilities.
 3. Themethod of claim 1 wherein: the UE comprises a visiting UE; the otherwireless communication network comprises a home wireless communicationnetwork for the visiting UE; and further comprising: an Access andMobility Management Function (AMF) determining that the UE comprises thevisiting UE and the other wireless communication network comprises thehome wireless communication network for the visiting UE, and inresponse, transferring the network ID of the home wireless communicationnetwork for the visiting UE to the UCMF.
 4. The method of claim 1wherein: the UE comprises a visiting UE; the other wirelesscommunication network comprises a home wireless communication networkfor the visiting UE; and further comprising: the UCMF determining thatthe UE comprises the visiting UE and the other wireless communicationnetwork comprises the home wireless communication network for thevisiting UE, wherein the UCMF transferring the UE capability data andthe network ID to the NEF comprises the UCMF transferring the UEcapability data and the network ID to the NEF in response to thedetermination that the UE comprises the visiting UE and the otherwireless communication network comprises the home wireless communicationnetwork for the visiting UE.
 5. The method of claim 1 wherein the UEcapability data and the additional UE capability data comprise RadioCapabilities Signaling Optimization (RACS) data.
 6. The method of claim1 wherein the UE capability data and the additional UE capability dataindicate Radio Access Technology (RAT) types.
 7. The method of claim 1wherein the UE capability data and the additional UE capability dataindicate frequency bands.
 8. The method of claim 1 wherein the UEcapability data and the additional UE capability data indicate wirelessnetwork slice types.
 9. The method of claim 1 wherein the UE capabilitydata and the additional UE capability data indicate user applications.10. The method of claim 1 wherein: the NEF transferring the UEcapability data to the other wireless communication network comprisestransferring the UE capability data to an Application Function (AF); theNEF receiving the UE capability request from the other wirelesscommunication network comprises receiving the UE capability request fromthe AF; the NEF transferring the additional UE capability data to theother wireless communication network comprises transferring theadditional UE capability data to the AF; and further comprising the AFreceiving the UE capability data from the NEF and responsivelytransferring the UE capability data to the other wireless communicationnetwork; the AF receiving the UE capability request from the otherwireless communication network and responsively transferring the UEcapability request data to the NEF; and the AF receiving the additionalUE capability data from the NEF and responsively transferring theadditional UE capability data to the other wireless communicationnetwork.
 11. A wireless communication network to serve a User Equipment(UE) and export UE capability data, the wireless communication networkcomprising: a UE Capability Management Function (UCMF) configured toreceive the UE capability data and a network Identifier (ID) andresponsively transfer the UE capability data and the network ID to aNetwork Exposure Function (NEF); the NEF configured to receive the UEcapability data and the network ID, and in response, transfer the UEcapability data to another wireless communication network based on thenetwork ID; the UCMF configured to receive additional UE capabilitydata; the NEF configured to receive a UE capability request for the UEfrom the other wireless communication network and responsively transferthe UE capability request for the UE to the UCMF; the UCMF configured toreceive the UE capability request and responsively transfer theadditional UE capability data to the NEF; and the NEF configured toreceive the additional UE capability data, and in response to the UEcapability request, transfer the additional UE capability data to theother wireless communication network.
 12. The wireless communicationnetwork of claim 11 wherein: the UE comprises a visiting UE; the otherwireless communication network comprises a home wireless communicationnetwork for the visiting UE; and the UE capability data comprises a UEcapability ID that is associated with a set of UE capabilities.
 13. Thewireless communication network of claim 11 wherein: the UE comprises avisiting UE; the other wireless communication network comprises a homewireless communication network for the visiting UE; and furthercomprising: an Access and Mobility Management Function (AMF) configuredto determine that the UE comprises the visiting UE and the otherwireless communication network comprises the home wireless communicationnetwork for the visiting UE, and in response, transfer the network ID ofthe home wireless communication network for the visiting UE to the UCMF.14. The wireless communication network of claim 11 wherein: the UEcomprises a visiting UE; the other wireless communication networkcomprises a home wireless communication network for the visiting UE; andfurther comprising: the UCMF configured to determine that the UEcomprises the visiting UE and the other wireless communication networkcomprises the home wireless communication network for the visiting UEand to transfer the UE capability data and the network ID to the NEF inresponse to the determination that the UE comprises the visiting UE andthe other wireless communication network comprises the home wirelesscommunication network for the visiting UE.
 15. The wirelesscommunication network of claim 11 wherein the UE capability data and theadditional UE capability data indicate Radio Capabilities SignalingOptimization (RACS) data.
 16. The wireless communication network ofclaim 11 wherein the UE capability data and the additional UE capabilitydata indicate Radio Access Technology (RAT) types.
 17. The wirelesscommunication network of claim 11 wherein the UE capability data and theadditional UE capability data indicate frequency bands.
 18. The wirelesscommunication network of claim 11 wherein the UE capability data and theadditional UE capability data indicate wireless network slice types. 19.The wireless communication network of claim 11 wherein the UE capabilitydata and the additional UE capability data indicate user applications.20. The wireless communication network of claim 11 wherein: the NEF isconfigured to transfer the UE capability data to an Application Function(AF); the NEF is configured to receive the UE capability request fromthe AF; the NEF is configured to transfer the additional UE capabilitydata to the AF; and further comprising the AF configured to receive theUE capability data from the NEF and responsively transfer the UEcapability data to the other wireless communication network; the AFconfigured to receive the UE capability request from the other wirelesscommunication network and responsively transfer the UE capabilityrequest data to the NEF; and the AF configured to receive the additionalUE capability data from the NEF and responsively transfer the additionalUE capability data to the other wireless communication network.